SMOODEV-2386: Maven Central publishing config for the Kotlin SDK#127
Merged
Conversation
Everything code-side for ai.smoo:smooai-config on Central: POM metadata (name/license/scm/developers), sources+javadoc jars, conditional PGP signing (skipped without the key so local dev and JitPack stay untouched — verified publishToMavenLocal still green), staging repo wiring, and a manual publish-kotlin workflow gated on the secrets. Remaining is account-side only: Sonatype Central account, ai.smoo namespace verification via smoo.ai DNS TXT, and four repo secrets. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MPVyaZaAGgvFRUq34z4qJ8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Code-side completion for publishing
ai.smoo:smooai-configto Maven Central:-sources/-javadocjarsMAVEN_SIGNING_KEYis present, so local dev and JitPack builds are untouched (verifiedpublishToMavenLocalstill green)OSSRH_USERNAME/PASSWORDPublish Kotlin SDKworkflow (version input), fail-loud when secrets are missingRemaining — account-side only (Brent, ~15 min once):
ai.smoonamespace — verification = one DNS TXT record on smoo.aiOSSRH_USERNAME+OSSRH_PASSWORDgpg --gen-key(or reuse) → export ASCII-armored private key →MAVEN_SIGNING_KEY+MAVEN_SIGNING_PASSWORD0.1.0— then the android app's JitPack pin swaps forai.smoo:smooai-config:0.1.0🤖 Generated with Claude Code
https://claude.ai/code/session_01MPVyaZaAGgvFRUq34z4qJ8